Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967b771c28d1ca1254f33b47c783b22cdfef58bc7a76e323251ef45f2d4002aa

Tx prefix hash: 396ebe06968a4fcbc62215d191e213374114562868b01e631d82f9f93574eedc
Tx public key: 847feaa37e3a183dc3007bb3e8f51974a54f643e93ecce25af0b2683cd9f2b3f
Timestamp: 1712637724 Timestamp [UCT]: 2024-04-09 04:42:04 Age [y:d:h:m:s]: 01:257:03:21:54
Block: 996495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442518 RingCT/type: yes/0
Extra: 01847feaa37e3a183dc3007bb3e8f51974a54f643e93ecce25af0b2683cd9f2b3f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a0c7f16d728ff47596acc8702e7739dfe7b048917d4782a7996d9ac1805fc0 0.600000000000 1456913 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": 996505, "vin": [ { "gen": { "height": 996495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a0c7f16d728ff47596acc8702e7739dfe7b048917d4782a7996d9ac1805fc0" } } ], "extra": [ 1, 132, 127, 234, 163, 126, 58, 24, 61, 195, 0, 123, 179, 232, 245, 25, 116, 165, 79, 100, 62, 147, 236, 206, 37, 175, 11, 38, 131, 205, 159, 43, 63, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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