Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85d144525dce6fa892e3bf02dd0d26f7868e08ca1229b4bc1a986454f0cbc0da

Tx prefix hash: bcf73d615f64275d5185472ab351bfa5ee83d20abd4fa1e3b5a240d76e9358b9
Tx public key: b9b636d67cf20b53b1cc29ae1a95c10ed3abc26557af025d72101d03a6990ac3
Timestamp: 1700443992 Timestamp [UCT]: 2023-11-20 01:33:12 Age [y:d:h:m:s]: 01:095:14:53:53
Block: 895426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329472 RingCT/type: yes/0
Extra: 01b9b636d67cf20b53b1cc29ae1a95c10ed3abc26557af025d72101d03a6990ac3021100000004faf35c9c000000000000000000

1 output(s) for total of 0.662341463000 dcy

stealth address amount amount idx
00: 48942ecee9baaced81cbeef29637bf31de4fcb18396949b01d5e7e3f67eeb369 0.662341463000 1351663 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": 895436, "vin": [ { "gen": { "height": 895426 } } ], "vout": [ { "amount": 662341463, "target": { "key": "48942ecee9baaced81cbeef29637bf31de4fcb18396949b01d5e7e3f67eeb369" } } ], "extra": [ 1, 185, 182, 54, 214, 124, 242, 11, 83, 177, 204, 41, 174, 26, 149, 193, 14, 211, 171, 194, 101, 87, 175, 2, 93, 114, 16, 29, 3, 166, 153, 10, 195, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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