Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b302589c8da588dc01173d3f6f5c415b5faa0ffea165c665b50933929eda36

Tx prefix hash: ae5dcb9e3781deeff9b597d9e89791fadcf36b8f5f3d15d6399587ac0ff278f3
Tx public key: 41140cd4789899567bc2282b095c4ef4d8cb76de1a7af1a8a16565d975e4a90c
Timestamp: 1702406723 Timestamp [UCT]: 2023-12-12 18:45:23 Age [y:d:h:m:s]: 01:194:04:35:05
Block: 911713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399711 RingCT/type: yes/0
Extra: 0141140cd4789899567bc2282b095c4ef4d8cb76de1a7af1a8a16565d975e4a90c02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4af319b0d2c8b30564b9055a017fd13a0cfaba1c255989d20e88937682d43cf 0.600000000000 1368929 of 15

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": 911723, "vin": [ { "gen": { "height": 911713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4af319b0d2c8b30564b9055a017fd13a0cfaba1c255989d20e88937682d43cf" } } ], "extra": [ 1, 65, 20, 12, 212, 120, 152, 153, 86, 123, 194, 40, 43, 9, 92, 78, 244, 216, 203, 118, 222, 26, 122, 241, 168, 161, 101, 101, 217, 117, 228, 169, 12, 2, 17, 0, 0, 0, 5, 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