Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2722c073a9d045e91fcf31d005310ee79e11e4b6faa25c294d96a061bf70b95

Tx prefix hash: b8dbd0ba197071442bcdf7ba3d15a168c8ca0034946b2d85c09c0e2b674574ec
Tx public key: 0a517b0a70394ffeea3172f9f15c607ae24a55a38e2a526be4aa89a4a4f93a3f
Timestamp: 1729556098 Timestamp [UCT]: 2024-10-22 00:14:58 Age [y:d:h:m:s]: 00:243:19:19:50
Block: 1136742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173897 RingCT/type: yes/0
Extra: 010a517b0a70394ffeea3172f9f15c607ae24a55a38e2a526be4aa89a4a4f93a3f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb193b79697f8c0457afda9db751b925b4c39faa181a9ad22f06bfd92cc53f07 0.600000000000 1620105 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": 1136752, "vin": [ { "gen": { "height": 1136742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb193b79697f8c0457afda9db751b925b4c39faa181a9ad22f06bfd92cc53f07" } } ], "extra": [ 1, 10, 81, 123, 10, 112, 57, 79, 254, 234, 49, 114, 249, 241, 92, 96, 122, 226, 74, 85, 163, 142, 42, 82, 107, 228, 170, 137, 164, 164, 249, 58, 63, 2, 17, 0, 0, 0, 1, 31, 10, 83, 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