Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d5311610035193815d7cd41fcd99bfe4049d3f2978a58ba37292368e7eec9e4

Tx prefix hash: a81cc7461eb61dc77a8f7c548a770c41a67a0671d5b03b45f127ac41baaa2006
Tx public key: 8cf18dcb3c149fcadc8c6655cbae512caf66bcbf4f3b99c0291ca5d17b167b0d
Timestamp: 1709177984 Timestamp [UCT]: 2024-02-29 03:39:44 Age [y:d:h:m:s]: 01:067:11:58:25
Block: 967841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309270 RingCT/type: yes/0
Extra: 018cf18dcb3c149fcadc8c6655cbae512caf66bcbf4f3b99c0291ca5d17b167b0d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0092c26edf1fee5b5ca8db107a20150354036a8ba178f2073a67c3bc515ccdd 0.600000000000 1427632 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": 967851, "vin": [ { "gen": { "height": 967841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0092c26edf1fee5b5ca8db107a20150354036a8ba178f2073a67c3bc515ccdd" } } ], "extra": [ 1, 140, 241, 141, 203, 60, 20, 159, 202, 220, 140, 102, 85, 203, 174, 81, 44, 175, 102, 188, 191, 79, 59, 153, 192, 41, 28, 165, 209, 123, 22, 123, 13, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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