Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0580d35148046a7ed827e4e8e2f8ef810b5762103d212213e2adcbbc3cf5e6b4

Tx prefix hash: ad6bd419f2da557429401b21484179e53cad80c91d3dd0b99aa7238321d110e1
Tx public key: 755fc580ee948fd86299c82578397411b447d6e1d8c9d093a74c42cc02ece5ff
Timestamp: 1722031955 Timestamp [UCT]: 2024-07-26 22:12:35 Age [y:d:h:m:s]: 00:288:09:09:46
Block: 1074391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206043 RingCT/type: yes/0
Extra: 01755fc580ee948fd86299c82578397411b447d6e1d8c9d093a74c42cc02ece5ff021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46eabb1b5cfa6e17b7dee33a29fe9f25d0b5f47765a3fbcfc3055d650f538bdd 0.600000000000 1546904 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": 1074401, "vin": [ { "gen": { "height": 1074391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46eabb1b5cfa6e17b7dee33a29fe9f25d0b5f47765a3fbcfc3055d650f538bdd" } } ], "extra": [ 1, 117, 95, 197, 128, 238, 148, 143, 216, 98, 153, 200, 37, 120, 57, 116, 17, 180, 71, 214, 225, 216, 201, 208, 147, 167, 76, 66, 204, 2, 236, 229, 255, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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