Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e339aad40598ee86a71c8448b0ec79b252e52f9a03164ccba3c25d313983df30

Tx prefix hash: f33a3d838c42dda1024fd33b34d356ec575b9e63c0178954df8cf437725fcd7d
Tx public key: cf90b84cf64f8fd0de08dbe3fac0cd3d683b24f05d156a7a6a0b29f1adeeddc3
Timestamp: 1741149059 Timestamp [UCT]: 2025-03-05 04:30:59 Age [y:d:h:m:s]: 00:258:13:00:40
Block: 1232429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182532 RingCT/type: yes/0
Extra: 01cf90b84cf64f8fd0de08dbe3fac0cd3d683b24f05d156a7a6a0b29f1adeeddc3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e309e0ed7b043ef9f3553319f681dc766f1b9e5e8d6538bb80410a8fca74855a 0.600000000000 1719342 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": 1232439, "vin": [ { "gen": { "height": 1232429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e309e0ed7b043ef9f3553319f681dc766f1b9e5e8d6538bb80410a8fca74855a" } } ], "extra": [ 1, 207, 144, 184, 76, 246, 79, 143, 208, 222, 8, 219, 227, 250, 192, 205, 61, 104, 59, 36, 240, 93, 21, 106, 122, 106, 11, 41, 241, 173, 238, 221, 195, 2, 17, 0, 0, 0, 2, 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