Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d550f2a3ca634a7f7df634fe999341285221780721d48d6bc5ce9c89ebcc11

Tx prefix hash: 3ef17947b9f9bca6d27a824b3c3b2359bd30e73f5588a4ffd47f84a7b1646b0b
Tx public key: 41a2b756935d83fadbbaf05da76c5a5b90a8fdde5066310ceeffff7e8d58a3b9
Timestamp: 1734433480 Timestamp [UCT]: 2024-12-17 11:04:40 Age [y:d:h:m:s]: 00:024:13:01:39
Block: 1177128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17522 RingCT/type: yes/0
Extra: 0141a2b756935d83fadbbaf05da76c5a5b90a8fdde5066310ceeffff7e8d58a3b9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eff3e0ab8b968967aaeefc578eea6634c1e49fed869f254cfffd39b762eab53d 0.600000000000 1663493 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": 1177138, "vin": [ { "gen": { "height": 1177128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eff3e0ab8b968967aaeefc578eea6634c1e49fed869f254cfffd39b762eab53d" } } ], "extra": [ 1, 65, 162, 183, 86, 147, 93, 131, 250, 219, 186, 240, 93, 167, 108, 90, 91, 144, 168, 253, 222, 80, 102, 49, 12, 238, 255, 255, 126, 141, 88, 163, 185, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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