Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1825bd57b1d6731001ac7a630b548e5770a3e5da99ee60768d6461a70c32b27d

Tx prefix hash: 369c9da41835af2a41a275e8ba2c6d2e9f97472bc28f02de65f1e10da889a88f
Tx public key: 072d22669cc926ed25c404c5ea1b5e1ae458b5f507ebc98a50f6495a63c4c6c3
Timestamp: 1706668945 Timestamp [UCT]: 2024-01-31 02:42:25 Age [y:d:h:m:s]: 01:100:22:41:40
Block: 947017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333239 RingCT/type: yes/0
Extra: 01072d22669cc926ed25c404c5ea1b5e1ae458b5f507ebc98a50f6495a63c4c6c30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e4128aefd27e62ff70f057a632003ca2c12f53540e7c9a5b53db87095b906a4 0.600000000000 1405363 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": 947027, "vin": [ { "gen": { "height": 947017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e4128aefd27e62ff70f057a632003ca2c12f53540e7c9a5b53db87095b906a4" } } ], "extra": [ 1, 7, 45, 34, 102, 156, 201, 38, 237, 37, 196, 4, 197, 234, 27, 94, 26, 228, 88, 181, 245, 7, 235, 201, 138, 80, 246, 73, 90, 99, 196, 198, 195, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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