Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7802e73a2ae88b1f334ec06d249d863beb8f406aae2eedbd1dad7c78517e3d5

Tx prefix hash: a17675350055ed13de0158cd3725925436268e400dd4bfd75d2c930f6c3378ed
Tx public key: 28a884b5f5fe2ebbb1fef5a2c4287e9f590ee962c4703d9a4eff62168fbc4b48
Timestamp: 1698026063 Timestamp [UCT]: 2023-10-23 01:54:23 Age [y:d:h:m:s]: 01:168:08:00:42
Block: 875587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381308 RingCT/type: yes/0
Extra: 0128a884b5f5fe2ebbb1fef5a2c4287e9f590ee962c4703d9a4eff62168fbc4b4802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.770578371000 dcy

stealth address amount amount idx
00: bdba5b68d33abf44ef43bdf90cc85d377d3e85c9271745c0a3f94495c16bf4e9 0.770578371000 1330849 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": 875597, "vin": [ { "gen": { "height": 875587 } } ], "vout": [ { "amount": 770578371, "target": { "key": "bdba5b68d33abf44ef43bdf90cc85d377d3e85c9271745c0a3f94495c16bf4e9" } } ], "extra": [ 1, 40, 168, 132, 181, 245, 254, 46, 187, 177, 254, 245, 162, 196, 40, 126, 159, 89, 14, 233, 98, 196, 112, 61, 154, 78, 255, 98, 22, 143, 188, 75, 72, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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