Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69760200ff174e9762c809f9390b0f27900dcc6e786e650cc085e7c0e7ff16e6

Tx prefix hash: 1afdf1f4e69f9095dde105afea3f5f77581e46ae9e7575948a500389ac5de556
Tx public key: 10c4215efea69d5e4714e7e25bdc35e3af66da5750ddce17d19364e1628d096f
Timestamp: 1581515169 Timestamp [UCT]: 2020-02-12 13:46:09 Age [y:d:h:m:s]: 04:267:16:02:30
Block: 63448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083435 RingCT/type: yes/0
Extra: 0110c4215efea69d5e4714e7e25bdc35e3af66da5750ddce17d19364e1628d096f02110000000212c4732d000000000000000000

1 output(s) for total of 378.243305974000 dcy

stealth address amount amount idx
00: 45f3798012f69be8ece0ee051f26f6a6a43d19d3f7f649240d4cf4f0c81247b9 378.243305974000 117002 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": 63458, "vin": [ { "gen": { "height": 63448 } } ], "vout": [ { "amount": 378243305974, "target": { "key": "45f3798012f69be8ece0ee051f26f6a6a43d19d3f7f649240d4cf4f0c81247b9" } } ], "extra": [ 1, 16, 196, 33, 94, 254, 166, 157, 94, 71, 20, 231, 226, 91, 220, 53, 227, 175, 102, 218, 87, 80, 221, 206, 23, 209, 147, 100, 225, 98, 141, 9, 111, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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