Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 430a3de7fa95d5d48ae430de7ab78e304d31901647878e06e2a3b17a19ffb07c

Tx prefix hash: f2d5274b08cae1145b527700204db82cf1c661094abcad7577258df6fe3071df
Tx public key: b1ebc6b5339ca75ea7fc5f8b2609a7ec0728e7e2f8eb4b608c5f45de5587437b
Timestamp: 1727482926 Timestamp [UCT]: 2024-09-28 00:22:06 Age [y:d:h:m:s]: 00:057:18:24:29
Block: 1119593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41279 RingCT/type: yes/0
Extra: 01b1ebc6b5339ca75ea7fc5f8b2609a7ec0728e7e2f8eb4b608c5f45de5587437b02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354dac313217489f7de00ac04b3d73fe38da309e8f62fead836e6cce2ba18432 0.600000000000 1601206 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": 1119603, "vin": [ { "gen": { "height": 1119593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354dac313217489f7de00ac04b3d73fe38da309e8f62fead836e6cce2ba18432" } } ], "extra": [ 1, 177, 235, 198, 181, 51, 156, 167, 94, 167, 252, 95, 139, 38, 9, 167, 236, 7, 40, 231, 226, 248, 235, 75, 96, 140, 95, 69, 222, 85, 135, 67, 123, 2, 17, 0, 0, 0, 9, 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