Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1dc17876debdb10e318239ad3aaaee411b9cf4b678172de1ccb1c2809662ed

Tx prefix hash: 7dfd027e318fad48ccc10174c4f9e13a2e79db65faec2394f1c3aac6f4d983d8
Tx public key: a37aa36d708817052af0ef40ce2904633f8ae958052b8ee2c54938ce61df437f
Timestamp: 1727973228 Timestamp [UCT]: 2024-10-03 16:33:48 Age [y:d:h:m:s]: 01:035:18:50:17
Block: 1123661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283948 RingCT/type: yes/0
Extra: 01a37aa36d708817052af0ef40ce2904633f8ae958052b8ee2c54938ce61df437f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2d007e1f6cfb14442d809b0ddb7de27e48672338b933314a1dfb0b21c17e3b9 0.600000000000 1606196 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": 1123671, "vin": [ { "gen": { "height": 1123661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2d007e1f6cfb14442d809b0ddb7de27e48672338b933314a1dfb0b21c17e3b9" } } ], "extra": [ 1, 163, 122, 163, 109, 112, 136, 23, 5, 42, 240, 239, 64, 206, 41, 4, 99, 63, 138, 233, 88, 5, 43, 142, 226, 197, 73, 56, 206, 97, 223, 67, 127, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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