Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da9838256f12c8e1786151295a29a1abb974578007f7c965b1c65ebd486c1b0e

Tx prefix hash: d20bc5d4d1c3005333f321abb7f7b9377431293aea374a922d6e403a3b2efbf9
Tx public key: baa801bf7226d518dc19b855695a44892dc1ae0a4ae6ea847af3daa6250dd4ab
Timestamp: 1681599855 Timestamp [UCT]: 2023-04-15 23:04:15 Age [y:d:h:m:s]: 01:184:21:55:07
Block: 739431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393673 RingCT/type: yes/0
Extra: 01baa801bf7226d518dc19b855695a44892dc1ae0a4ae6ea847af3daa6250dd4ab021100000002b3164c24000000000000000000

1 output(s) for total of 2.177501000000 dcy

stealth address amount amount idx
00: 758ddc61d68f3aecb2695c59ed33c4d71dcc3b0c1a7c9b1fd5c94d7d41c7406f 2.177501000000 1186282 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": 739441, "vin": [ { "gen": { "height": 739431 } } ], "vout": [ { "amount": 2177501000, "target": { "key": "758ddc61d68f3aecb2695c59ed33c4d71dcc3b0c1a7c9b1fd5c94d7d41c7406f" } } ], "extra": [ 1, 186, 168, 1, 191, 114, 38, 213, 24, 220, 25, 184, 85, 105, 90, 68, 137, 45, 193, 174, 10, 74, 230, 234, 132, 122, 243, 218, 166, 37, 13, 212, 171, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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