Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b1a56d7ae40ea909d091acaba81b03757015bc502c2c0770d019815fe2a62a

Tx prefix hash: 5516bd958fc6860df1c8137497fca1d8706b688fbc5b04aee7ea5df549218dc6
Tx public key: ed348672f1b63c0c76037cbdd7d3fe67bf5a0efc8bb545151e1157a90aed444d
Timestamp: 1706386152 Timestamp [UCT]: 2024-01-27 20:09:12 Age [y:d:h:m:s]: 01:080:10:08:30
Block: 944662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318576 RingCT/type: yes/0
Extra: 01ed348672f1b63c0c76037cbdd7d3fe67bf5a0efc8bb545151e1157a90aed444d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6979f22a159c4ff338716e5e686708ef00b33da7ee39e49c8e1227bb5b8cc5f3 0.600000000000 1402948 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": 944672, "vin": [ { "gen": { "height": 944662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6979f22a159c4ff338716e5e686708ef00b33da7ee39e49c8e1227bb5b8cc5f3" } } ], "extra": [ 1, 237, 52, 134, 114, 241, 182, 60, 12, 118, 3, 124, 189, 215, 211, 254, 103, 191, 90, 14, 252, 139, 181, 69, 21, 30, 17, 87, 169, 10, 237, 68, 77, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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