Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa8fa840a39d7c0fd3d1d43409fcd326bf53b197af787b248612cf6d8571dab

Tx prefix hash: dedb6d4f34823c9dfbc1381f46506aea10800552db028311d4bbad090b17070a
Tx public key: dd01dcf8d704e7568eca70e932cd16f6aef0f710d82ce7a3b86bfe0ef9f0aa25
Timestamp: 1695676105 Timestamp [UCT]: 2023-09-25 21:08:25 Age [y:d:h:m:s]: 01:266:05:21:18
Block: 856095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451261 RingCT/type: yes/0
Extra: 01dd01dcf8d704e7568eca70e932cd16f6aef0f710d82ce7a3b86bfe0ef9f0aa25021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.894132603000 dcy

stealth address amount amount idx
00: 3aa494cc1d11e72ae94ec08710e6099d4fe6e25cc528ae3f3002e5b5b2a1c796 0.894132603000 1310153 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": 856105, "vin": [ { "gen": { "height": 856095 } } ], "vout": [ { "amount": 894132603, "target": { "key": "3aa494cc1d11e72ae94ec08710e6099d4fe6e25cc528ae3f3002e5b5b2a1c796" } } ], "extra": [ 1, 221, 1, 220, 248, 215, 4, 231, 86, 142, 202, 112, 233, 50, 205, 22, 246, 174, 240, 247, 16, 216, 44, 231, 163, 184, 107, 254, 14, 249, 240, 170, 37, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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