Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: becbf2b897f202a80b7bab58fcc8c9dbf30d599873419fbb5e34a19c73f92d7e

Tx prefix hash: ffa4c6b09fda64f7656ddbd9106fb02c954daeb12c1f2c838907ab7e8b21ff2d
Tx public key: 3ebbe3226fdf6a9e7957084b533e9e02ab89d80598983d2e717cd5770ae6376b
Timestamp: 1578080294 Timestamp [UCT]: 2020-01-03 19:38:14 Age [y:d:h:m:s]: 04:364:20:12:40
Block: 37945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150025 RingCT/type: yes/0
Extra: 013ebbe3226fdf6a9e7957084b533e9e02ab89d80598983d2e717cd5770ae6376b02110000000d4ac5aa02000000000000000000

1 output(s) for total of 459.487090219000 dcy

stealth address amount amount idx
00: 42505e35aae9c66d9c7d576ba243b75000bb1af978a3f834522096762f4a7910 459.487090219000 64522 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": 37955, "vin": [ { "gen": { "height": 37945 } } ], "vout": [ { "amount": 459487090219, "target": { "key": "42505e35aae9c66d9c7d576ba243b75000bb1af978a3f834522096762f4a7910" } } ], "extra": [ 1, 62, 187, 227, 34, 111, 223, 106, 158, 121, 87, 8, 75, 83, 62, 158, 2, 171, 137, 216, 5, 152, 152, 61, 46, 113, 124, 213, 119, 10, 230, 55, 107, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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