Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e257af895f694914f5f6760e6df5c9255e861202e47f820e90855d02b25594

Tx prefix hash: 70ce1cc60a07b5c6dad14d9129e268e7ebcebf940fd3e1ef9060ef57db1b8da0
Tx public key: 512ac0f17858ecdf2110625f6e10f346355825ca9e110f009c3a85ae364eba16
Timestamp: 1694273509 Timestamp [UCT]: 2023-09-09 15:31:49 Age [y:d:h:m:s]: 01:217:10:49:50
Block: 844453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416537 RingCT/type: yes/0
Extra: 01512ac0f17858ecdf2110625f6e10f346355825ca9e110f009c3a85ae364eba1602110000000433af99f4000000000000000000

1 output(s) for total of 0.977184853000 dcy

stealth address amount amount idx
00: dcee301f2ab5cbef98628d4a4d28c307bc9e4e8e7ef548cd172f1f7ccdba59d2 0.977184853000 1297763 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": 844463, "vin": [ { "gen": { "height": 844453 } } ], "vout": [ { "amount": 977184853, "target": { "key": "dcee301f2ab5cbef98628d4a4d28c307bc9e4e8e7ef548cd172f1f7ccdba59d2" } } ], "extra": [ 1, 81, 42, 192, 241, 120, 88, 236, 223, 33, 16, 98, 95, 110, 16, 243, 70, 53, 88, 37, 202, 158, 17, 15, 0, 156, 58, 133, 174, 54, 78, 186, 22, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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