Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65584bc4a75dba5c08d53186a3ddf1d0bb6042e1250ec6c0f703bb67753cc150

Tx prefix hash: 225d84983d743e8c065ee720c9262cd1d8ef726b97ab81d4bfe526e359f7d40e
Tx public key: 3cae2b6093f1c46f08fe4472fbe848a898edc50c3eeb749f558dc60a9b012a4f
Timestamp: 1607856270 Timestamp [UCT]: 2020-12-13 10:44:30 Age [y:d:h:m:s]: 04:322:21:49:11
Block: 161151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1240662 RingCT/type: yes/0
Extra: 013cae2b6093f1c46f08fe4472fbe848a898edc50c3eeb749f558dc60a9b012a4f02110000018cc6b81c9d000000000000000000

1 output(s) for total of 179.490107963000 dcy

stealth address amount amount idx
00: bb0e5c6a1515f295e305d3fe4b4d3c425b26c62d937c8bb15bfd8470f51fe09b 179.490107963000 285014 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": 161161, "vin": [ { "gen": { "height": 161151 } } ], "vout": [ { "amount": 179490107963, "target": { "key": "bb0e5c6a1515f295e305d3fe4b4d3c425b26c62d937c8bb15bfd8470f51fe09b" } } ], "extra": [ 1, 60, 174, 43, 96, 147, 241, 196, 111, 8, 254, 68, 114, 251, 232, 72, 168, 152, 237, 197, 12, 62, 235, 116, 159, 85, 141, 198, 10, 155, 1, 42, 79, 2, 17, 0, 0, 1, 140, 198, 184, 28, 157, 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