Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec1baf439fa9b84fd7bb6c06dd4316039380365fe910a5e4d403816bb13b4e2

Tx prefix hash: e02be59275bd3a3009d7fddc6123b44b37504723fcd6ff03bc44aa7a85ca2b78
Tx public key: 64227d3ccc7b9cded8afc9e31968b71050dd548945abd6dd0e8046fd21e0aace
Timestamp: 1735599100 Timestamp [UCT]: 2024-12-30 22:51:40 Age [y:d:h:m:s]: 00:169:03:32:29
Block: 1186748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120607 RingCT/type: yes/0
Extra: 0164227d3ccc7b9cded8afc9e31968b71050dd548945abd6dd0e8046fd21e0aace021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26010837ce60a00f41b9b449506d95a558dcf03de783e234f8c1e2ac8bb4fd73 0.600000000000 1673233 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": 1186758, "vin": [ { "gen": { "height": 1186748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26010837ce60a00f41b9b449506d95a558dcf03de783e234f8c1e2ac8bb4fd73" } } ], "extra": [ 1, 100, 34, 125, 60, 204, 123, 156, 222, 216, 175, 201, 227, 25, 104, 183, 16, 80, 221, 84, 137, 69, 171, 214, 221, 14, 128, 70, 253, 33, 224, 170, 206, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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