Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29fa012a69f98e032402ef4fee71f0ed6212217162ef2b8d341a9047a8cda308

Tx prefix hash: 49a225fe9bdc239329f82ab83b903a7723d85b9249b149466cf361ea09956c05
Tx public key: f7595c25e85b5d5a45d3131da4976f74a9dc76cb2f9cce8491f8c8df3ddd52a2
Timestamp: 1674953485 Timestamp [UCT]: 2023-01-29 00:51:25 Age [y:d:h:m:s]: 02:114:14:03:05
Block: 684967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 603574 RingCT/type: yes/0
Extra: 01f7595c25e85b5d5a45d3131da4976f74a9dc76cb2f9cce8491f8c8df3ddd52a20211000000015029cbac000000000000000000

1 output(s) for total of 3.299285672000 dcy

stealth address amount amount idx
00: 17b2c7c7a0a2f1c0db9ac49b0cb44f8e399aa040826ac6d1955b3d8e050bc3ef 3.299285672000 1127250 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": 684977, "vin": [ { "gen": { "height": 684967 } } ], "vout": [ { "amount": 3299285672, "target": { "key": "17b2c7c7a0a2f1c0db9ac49b0cb44f8e399aa040826ac6d1955b3d8e050bc3ef" } } ], "extra": [ 1, 247, 89, 92, 37, 232, 91, 93, 90, 69, 211, 19, 29, 164, 151, 111, 116, 169, 220, 118, 203, 47, 156, 206, 132, 145, 248, 200, 223, 61, 221, 82, 162, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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