Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 452c64ba469f3d6581eee254c8406bc9d5ea45ab232cb2fe5e58f371acac68c2

Tx prefix hash: c6aa67b2294eb69f0d1772264ab6669acf32e2490ea7e1c15c5929f87f9bffb9
Tx public key: 3d1488daa063b8e9efca06f0cecef8e10c1930d9d749b6b1e77b302ca63fac27
Timestamp: 1740880768 Timestamp [UCT]: 2025-03-02 01:59:28 Age [y:d:h:m:s]: 00:260:11:16:11
Block: 1230204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183910 RingCT/type: yes/0
Extra: 013d1488daa063b8e9efca06f0cecef8e10c1930d9d749b6b1e77b302ca63fac27021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e41780557943abe92337f78ff97f7be96a148f7e30d4f046b60d91b82a253e15 0.600000000000 1717101 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": 1230214, "vin": [ { "gen": { "height": 1230204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e41780557943abe92337f78ff97f7be96a148f7e30d4f046b60d91b82a253e15" } } ], "extra": [ 1, 61, 20, 136, 218, 160, 99, 184, 233, 239, 202, 6, 240, 206, 206, 248, 225, 12, 25, 48, 217, 215, 73, 182, 177, 231, 123, 48, 44, 166, 63, 172, 39, 2, 17, 0, 0, 0, 2, 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