Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d32c0213044f64a435da7a6e02454435c238b4b5648488cbe58574eb79caea

Tx prefix hash: 872b493727caa0aefb2def1dd75612a43fbc656bdfa7136c67543b1cf1db1d5d
Tx public key: 7e83709a2e62e786c088b42d7945f784ae11d27e1c16df885876f6af2fc38f29
Timestamp: 1727882323 Timestamp [UCT]: 2024-10-02 15:18:43 Age [y:d:h:m:s]: 00:238:11:06:39
Block: 1122912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170266 RingCT/type: yes/0
Extra: 017e83709a2e62e786c088b42d7945f784ae11d27e1c16df885876f6af2fc38f29021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6919b0052adc4cf43eba4f852efd3d79502ce7912c090017bd1a437f55f1df19 0.600000000000 1605445 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": 1122922, "vin": [ { "gen": { "height": 1122912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6919b0052adc4cf43eba4f852efd3d79502ce7912c090017bd1a437f55f1df19" } } ], "extra": [ 1, 126, 131, 112, 154, 46, 98, 231, 134, 192, 136, 180, 45, 121, 69, 247, 132, 174, 17, 210, 126, 28, 22, 223, 136, 88, 118, 246, 175, 47, 195, 143, 41, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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