Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472efda316581c23524457680308bd52e6ae779610b4969d4d9aac9f33b3b007

Tx prefix hash: 7617f6555b1b52f04dd42835061323734a1b52d27cdd5d1fc53e1b4f25582fc7
Tx public key: cf9f2481c91ef69aa76a8baa5148168f71196be6bf259d0bd06e6481e8140665
Timestamp: 1643589676 Timestamp [UCT]: 2022-01-31 00:41:16 Age [y:d:h:m:s]: 02:340:06:16:30
Block: 428843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761734 RingCT/type: yes/0
Extra: 01cf9f2481c91ef69aa76a8baa5148168f71196be6bf259d0bd06e6481e8140665021100000009cb8520c2000000000000000000

1 output(s) for total of 23.284420277000 dcy

stealth address amount amount idx
00: 3ec2e2fa2f8c1727b2d5d305493c49583fc236bed030aaca30873fd130257c4d 23.284420277000 838341 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": 428853, "vin": [ { "gen": { "height": 428843 } } ], "vout": [ { "amount": 23284420277, "target": { "key": "3ec2e2fa2f8c1727b2d5d305493c49583fc236bed030aaca30873fd130257c4d" } } ], "extra": [ 1, 207, 159, 36, 129, 201, 30, 246, 154, 167, 106, 139, 170, 81, 72, 22, 143, 113, 25, 107, 230, 191, 37, 157, 11, 208, 110, 100, 129, 232, 20, 6, 101, 2, 17, 0, 0, 0, 9, 203, 133, 32, 194, 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