Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 269fc743f2bc9b4162ac99c08884cdd6c7968cb7dd0772a11b5eeaae55a7aa80

Tx prefix hash: 24e88686712d5ac94d05b9b5f9b525a1ac58180f5c940cd01aaf9257722af80d
Tx public key: e9720a73cca0ea0afc41cfda1728b8d8cd10095017854b406279e4791b947fc9
Timestamp: 1699407300 Timestamp [UCT]: 2023-11-08 01:35:00 Age [y:d:h:m:s]: 01:171:23:53:30
Block: 886835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384131 RingCT/type: yes/0
Extra: 01e9720a73cca0ea0afc41cfda1728b8d8cd10095017854b406279e4791b947fc902110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.707208554000 dcy

stealth address amount amount idx
00: aedcca8d38f82cd128a6c4c28d2a6541569abdee51f5a8646dcee6281bb4a6ca 0.707208554000 1342682 of 0

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": 886845, "vin": [ { "gen": { "height": 886835 } } ], "vout": [ { "amount": 707208554, "target": { "key": "aedcca8d38f82cd128a6c4c28d2a6541569abdee51f5a8646dcee6281bb4a6ca" } } ], "extra": [ 1, 233, 114, 10, 115, 204, 160, 234, 10, 252, 65, 207, 218, 23, 40, 184, 216, 205, 16, 9, 80, 23, 133, 75, 64, 98, 121, 228, 121, 27, 148, 127, 201, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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