Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2931926be964ed2e2505691fa25fb40066cbfe768bac5835b4027c85c6c82cd0

Tx prefix hash: 1494a077f0995020cd19e135130ad1c275093e5edd8399df6529018a40f4b5f3
Tx public key: 1e40f89aa80d25fa52b166e203df05e8a5a3478d634bb7044e72d70cdcc3aaf5
Timestamp: 1712342630 Timestamp [UCT]: 2024-04-05 18:43:50 Age [y:d:h:m:s]: 01:072:00:37:52
Block: 994038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312406 RingCT/type: yes/0
Extra: 011e40f89aa80d25fa52b166e203df05e8a5a3478d634bb7044e72d70cdcc3aaf502110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91f5f25a60b3914d4b21b4e41ba992c4f1079f88eae449dc33c68a59e36c7b9c 0.600000000000 1454434 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 994048, "vin": [ { "gen": { "height": 994038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91f5f25a60b3914d4b21b4e41ba992c4f1079f88eae449dc33c68a59e36c7b9c" } } ], "extra": [ 1, 30, 64, 248, 154, 168, 13, 37, 250, 82, 177, 102, 226, 3, 223, 5, 232, 165, 163, 71, 141, 99, 75, 183, 4, 78, 114, 215, 12, 220, 195, 170, 245, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8