Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985cc7be0995960daa49e7691d0c5db2c834ffd964e20769a05a860e15cd84c1

Tx prefix hash: 6fd2764dbc04a453e65e95c51db0c9d195bf4768653030308ac35343236171f8
Tx public key: 0af25c1ba7e05402a7d9b73fc6c00f805688f12ac66fd0ba97d975f5dd6354cb
Timestamp: 1689774789 Timestamp [UCT]: 2023-07-19 13:53:09 Age [y:d:h:m:s]: 02:116:06:16:32
Block: 807235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602787 RingCT/type: yes/0
Extra: 010af25c1ba7e05402a7d9b73fc6c00f805688f12ac66fd0ba97d975f5dd6354cb02110000000833af99f4000000000000000000

1 output(s) for total of 1.298062086000 dcy

stealth address amount amount idx
00: 9bff71a0cd71fb4691f72e3a0b3e4ca78b2e791f4199d3f2169a4ae2b1bd9d3f 1.298062086000 1258782 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": 807245, "vin": [ { "gen": { "height": 807235 } } ], "vout": [ { "amount": 1298062086, "target": { "key": "9bff71a0cd71fb4691f72e3a0b3e4ca78b2e791f4199d3f2169a4ae2b1bd9d3f" } } ], "extra": [ 1, 10, 242, 92, 27, 167, 224, 84, 2, 167, 217, 183, 63, 198, 192, 15, 128, 86, 136, 241, 42, 198, 111, 208, 186, 151, 217, 117, 245, 221, 99, 84, 203, 2, 17, 0, 0, 0, 8, 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