Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 103a0ab3dc736998c2b7c34d150eb6221def14d23e1f23e149bafe8e4f092f4a

Tx prefix hash: b58a65ef977c6f8eb9c46d01d4754f199e6734b1b6001c787e9bb0549a0678e6
Tx public key: 38ae705efeb05bdb9331e9cbee1731fbb59c43e11ee0f49a5c0ef0097b1123f3
Timestamp: 1736269325 Timestamp [UCT]: 2025-01-07 17:02:05 Age [y:d:h:m:s]: 00:296:19:41:42
Block: 1192299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209639 RingCT/type: yes/0
Extra: 0138ae705efeb05bdb9331e9cbee1731fbb59c43e11ee0f49a5c0ef0097b1123f302110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eedfcaa9bd0a95d390f15ceb7442f3c61e2721eaa4f9871710496ba03995420f 0.600000000000 1678848 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": 1192309, "vin": [ { "gen": { "height": 1192299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eedfcaa9bd0a95d390f15ceb7442f3c61e2721eaa4f9871710496ba03995420f" } } ], "extra": [ 1, 56, 174, 112, 94, 254, 176, 91, 219, 147, 49, 233, 203, 238, 23, 49, 251, 181, 156, 67, 225, 30, 224, 244, 154, 92, 14, 240, 9, 123, 17, 35, 243, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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