Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071a3d3551f7b1f92e2e8a9ad2b9261c003a123ac2781910e2b9b193a2f2d0a2

Tx prefix hash: b9406c2d086a4212ec3b6ca174ae1bc6facec586367ff71ec2e4ac1447583bd6
Tx public key: 744ae7d2ed6084c4f32549dfa4ed1753b90404dff28cd240b91ca2b891a478da
Timestamp: 1695758415 Timestamp [UCT]: 2023-09-26 20:00:15 Age [y:d:h:m:s]: 02:039:18:50:28
Block: 856779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548076 RingCT/type: yes/0
Extra: 01744ae7d2ed6084c4f32549dfa4ed1753b90404dff28cd240b91ca2b891a478da0211000000114b8f5122000000000000000000

1 output(s) for total of 0.889478702000 dcy

stealth address amount amount idx
00: 1a0f9367d6793481285fdc52853c78387b7a487ada78717720cc0775f5970ec3 0.889478702000 1310867 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": 856789, "vin": [ { "gen": { "height": 856779 } } ], "vout": [ { "amount": 889478702, "target": { "key": "1a0f9367d6793481285fdc52853c78387b7a487ada78717720cc0775f5970ec3" } } ], "extra": [ 1, 116, 74, 231, 210, 237, 96, 132, 196, 243, 37, 73, 223, 164, 237, 23, 83, 185, 4, 4, 223, 242, 140, 210, 64, 185, 28, 162, 184, 145, 164, 120, 218, 2, 17, 0, 0, 0, 17, 75, 143, 81, 34, 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