Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9f9d38f7afdf74d9d7334069f786b4d7ec99cc76dff1aa809b0c60f9e931d7

Tx prefix hash: 33643e6cfbdeb677655ea0b5c3afda02b7ab059059e0115de1ac0e4973d4eb89
Tx public key: 6b1a14710a7bf1170c258407504a5eb1a0816bdd6f95ed47695abf00b6a8a74c
Timestamp: 1700971304 Timestamp [UCT]: 2023-11-26 04:01:44 Age [y:d:h:m:s]: 01:134:12:01:47
Block: 899795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357297 RingCT/type: yes/0
Extra: 016b1a14710a7bf1170c258407504a5eb1a0816bdd6f95ed47695abf00b6a8a74c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.640627571000 dcy

stealth address amount amount idx
00: 98ed1f8136a25dc2ef374a0aa6fcb73a4de2c5f84719f3f2e97ef9596052aa82 0.640627571000 1356258 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": 899805, "vin": [ { "gen": { "height": 899795 } } ], "vout": [ { "amount": 640627571, "target": { "key": "98ed1f8136a25dc2ef374a0aa6fcb73a4de2c5f84719f3f2e97ef9596052aa82" } } ], "extra": [ 1, 107, 26, 20, 113, 10, 123, 241, 23, 12, 37, 132, 7, 80, 74, 94, 177, 160, 129, 107, 221, 111, 149, 237, 71, 105, 90, 191, 0, 182, 168, 167, 76, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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