Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9b1d0f5faf1306c076f724530a64a54ac1f850b0862badf80c7dfde47d83cb1

Tx prefix hash: ad114401777788aa7dca134d8d4003ea590631fbdc22935bb4c4f8a9657e7e34
Tx public key: 4bb5730d8440bbcbbe50960491f618b91c15bd737b0b557ea5f9bec9f8c1e20b
Timestamp: 1719928700 Timestamp [UCT]: 2024-07-02 13:58:20 Age [y:d:h:m:s]: 00:276:16:57:45
Block: 1056967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197708 RingCT/type: yes/0
Extra: 014bb5730d8440bbcbbe50960491f618b91c15bd737b0b557ea5f9bec9f8c1e20b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4345fe7bc9469a70f29e7403177dbd7b56e81f36ce9714a4dbbcd6430ec4e1d6 0.600000000000 1527396 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": 1056977, "vin": [ { "gen": { "height": 1056967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4345fe7bc9469a70f29e7403177dbd7b56e81f36ce9714a4dbbcd6430ec4e1d6" } } ], "extra": [ 1, 75, 181, 115, 13, 132, 64, 187, 203, 190, 80, 150, 4, 145, 246, 24, 185, 28, 21, 189, 115, 123, 11, 85, 126, 165, 249, 190, 201, 248, 193, 226, 11, 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