Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ef55c0728d8fbc4bea0cdeb9d6dd506b07242040dc7909c495ae57e7b99cc84

Tx prefix hash: 158fbc8f6b2b98104eec21ce242fb828302f776d7ae24f398782f7771c11dfa0
Tx public key: 07e9c1c4bc2923587ddeb653518e1eb37594568023b4f3ef1745fd9a830142ad
Timestamp: 1734161973 Timestamp [UCT]: 2024-12-14 07:39:33 Age [y:d:h:m:s]: 00:186:20:21:23
Block: 1174876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133216 RingCT/type: yes/0
Extra: 0107e9c1c4bc2923587ddeb653518e1eb37594568023b4f3ef1745fd9a830142ad0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 572c9ed2749e5339fa94399d0646068151c2a1e88d2ccb532fdf5e4bb8b9ab16 0.600000000000 1661081 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": 1174886, "vin": [ { "gen": { "height": 1174876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "572c9ed2749e5339fa94399d0646068151c2a1e88d2ccb532fdf5e4bb8b9ab16" } } ], "extra": [ 1, 7, 233, 193, 196, 188, 41, 35, 88, 125, 222, 182, 83, 81, 142, 30, 179, 117, 148, 86, 128, 35, 180, 243, 239, 23, 69, 253, 154, 131, 1, 66, 173, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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