Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6ff9e7b8181444faba939fdc1647b007c95df32e2adc1869f2b830d9c365fb

Tx prefix hash: d329eae59c36f8788e61d49a70bea869d54b902dff0ed87483146026f98b3b5d
Tx public key: 985f9c72b1a431f59723942c315f0c78bdd853ab61660bc1c9f27f1503f6d8f4
Timestamp: 1672655106 Timestamp [UCT]: 2023-01-02 10:25:06 Age [y:d:h:m:s]: 01:318:07:29:51
Block: 665903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488493 RingCT/type: yes/0
Extra: 01985f9c72b1a431f59723942c315f0c78bdd853ab61660bc1c9f27f1503f6d8f402110000000152542ceb000000000000000000

1 output(s) for total of 3.815811344000 dcy

stealth address amount amount idx
00: ef419bf9e8f6fef37fe62e28f8907d9dffe220ae6d628198b9a40dfa3cbfb061 3.815811344000 1106972 of 0

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": 665913, "vin": [ { "gen": { "height": 665903 } } ], "vout": [ { "amount": 3815811344, "target": { "key": "ef419bf9e8f6fef37fe62e28f8907d9dffe220ae6d628198b9a40dfa3cbfb061" } } ], "extra": [ 1, 152, 95, 156, 114, 177, 164, 49, 245, 151, 35, 148, 44, 49, 95, 12, 120, 189, 216, 83, 171, 97, 102, 11, 193, 201, 242, 127, 21, 3, 246, 216, 244, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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