Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c1d961b74ba694e41731038ffb3335d9c197cd2d1000a38bf3994268186065

Tx prefix hash: fe32154bade3fe8dbdec3a8417f103ea5d75e6ad42887463445b4aee29e44d6e
Tx public key: 2e96a48ce88767508688dd314d8959edb7bdf3470f9e98bc3e058d1a5a844d2d
Timestamp: 1639745026 Timestamp [UCT]: 2021-12-17 12:43:46 Age [y:d:h:m:s]: 03:020:16:15:01
Block: 397485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 793753 RingCT/type: yes/0
Extra: 012e96a48ce88767508688dd314d8959edb7bdf3470f9e98bc3e058d1a5a844d2d0211000000010eb261b4000000000000000000

1 output(s) for total of 29.578434298000 dcy

stealth address amount amount idx
00: e9de126fc6df7f68545b241c6c720c5ea75593a2fd9f588f37eee90edab526cd 29.578434298000 796094 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": 397495, "vin": [ { "gen": { "height": 397485 } } ], "vout": [ { "amount": 29578434298, "target": { "key": "e9de126fc6df7f68545b241c6c720c5ea75593a2fd9f588f37eee90edab526cd" } } ], "extra": [ 1, 46, 150, 164, 140, 232, 135, 103, 80, 134, 136, 221, 49, 77, 137, 89, 237, 183, 189, 243, 71, 15, 158, 152, 188, 62, 5, 141, 26, 90, 132, 77, 45, 2, 17, 0, 0, 0, 1, 14, 178, 97, 180, 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