Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c739c56bf45b2fb77e8e17113d4203c5b844e15a53c8611158bf53b607b909c2

Tx prefix hash: 74f1e9d8f684f3760c3480eb6e429cfe83914612058550b4a35fef9b3d5a2b7b
Tx public key: 10b4a2051977d1ad988202a2048b5b750b57ca0b75beb1691b5a3316e443fedc
Timestamp: 1633205134 Timestamp [UCT]: 2021-10-02 20:05:34 Age [y:d:h:m:s]: 03:159:17:51:31
Block: 345349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890959 RingCT/type: yes/0
Extra: 0110b4a2051977d1ad988202a2048b5b750b57ca0b75beb1691b5a3316e443fedc0211000000018d0de867000000000000000000

1 output(s) for total of 44.027429305000 dcy

stealth address amount amount idx
00: d9d9db0684cbdd4d4eb7babbfc1ed7b0a80ef3cf27534acb4891e26ce96ff620 44.027429305000 708477 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": 345359, "vin": [ { "gen": { "height": 345349 } } ], "vout": [ { "amount": 44027429305, "target": { "key": "d9d9db0684cbdd4d4eb7babbfc1ed7b0a80ef3cf27534acb4891e26ce96ff620" } } ], "extra": [ 1, 16, 180, 162, 5, 25, 119, 209, 173, 152, 130, 2, 162, 4, 139, 91, 117, 11, 87, 202, 11, 117, 190, 177, 105, 27, 90, 51, 22, 228, 67, 254, 220, 2, 17, 0, 0, 0, 1, 141, 13, 232, 103, 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