Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0889e0e95034bf10084e69e818e60385d5415bda717469122bc307c6d9c3db34

Tx prefix hash: 142cba1fc612131cfcf94fb550d51b9a32dfb4a7327ad575a8bcb8c7f6bfab28
Tx public key: 717fda4608db3cf9c1b72243871276fa413b70cef88aa0cad1efd8a330646f6b
Timestamp: 1697276313 Timestamp [UCT]: 2023-10-14 09:38:33 Age [y:d:h:m:s]: 01:220:11:44:28
Block: 869365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418660 RingCT/type: yes/0
Extra: 01717fda4608db3cf9c1b72243871276fa413b70cef88aa0cad1efd8a330646f6b02110000000333af99f4000000000000000000

1 output(s) for total of 0.808040061000 dcy

stealth address amount amount idx
00: 903e204d1d3778ecbd3826612a3915b4993f6c076338894ab485e92a999a404e 0.808040061000 1324210 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": 869375, "vin": [ { "gen": { "height": 869365 } } ], "vout": [ { "amount": 808040061, "target": { "key": "903e204d1d3778ecbd3826612a3915b4993f6c076338894ab485e92a999a404e" } } ], "extra": [ 1, 113, 127, 218, 70, 8, 219, 60, 249, 193, 183, 34, 67, 135, 18, 118, 250, 65, 59, 112, 206, 248, 138, 160, 202, 209, 239, 216, 163, 48, 100, 111, 107, 2, 17, 0, 0, 0, 3, 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