Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40f3c947f33a368f8a293a71c5f586acd8c53704cbb02a225beb61e364aab72a

Tx prefix hash: 76c501a6cfa4a5216f5af6bc788dfbf24ab3f9da1e944c4e1384d0e24d7c29ad
Tx public key: 36e918d2bd835aa0ef48e724dfd24255aef11f2c7c81a15b33fee7afd9ee91b4
Timestamp: 1699280337 Timestamp [UCT]: 2023-11-06 14:18:57 Age [y:d:h:m:s]: 02:000:13:58:41
Block: 885785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520165 RingCT/type: yes/0
Extra: 0136e918d2bd835aa0ef48e724dfd24255aef11f2c7c81a15b33fee7afd9ee91b4021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.712896680000 dcy

stealth address amount amount idx
00: 295d6e964005154660307276f6de17cebcc612f37e4061c6b8da61d2f776fc14 0.712896680000 1341572 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": 885795, "vin": [ { "gen": { "height": 885785 } } ], "vout": [ { "amount": 712896680, "target": { "key": "295d6e964005154660307276f6de17cebcc612f37e4061c6b8da61d2f776fc14" } } ], "extra": [ 1, 54, 233, 24, 210, 189, 131, 90, 160, 239, 72, 231, 36, 223, 210, 66, 85, 174, 241, 31, 44, 124, 129, 161, 91, 51, 254, 231, 175, 217, 238, 145, 180, 2, 17, 0, 0, 0, 6, 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