Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505291db942a6882b91f1fe0cb216e10ff226b986809a5d472e4804a43294b94

Tx prefix hash: 3572f8e938673e2878a3053b935f31481e79248b6a44630a524c46fc6acdefec
Tx public key: c24a91e80fb4bcf0a3386b1d172c61a11d47f891f1b476230c465c800a5d266b
Timestamp: 1711409094 Timestamp [UCT]: 2024-03-25 23:24:54 Age [y:d:h:m:s]: 01:081:08:02:49
Block: 986359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319030 RingCT/type: yes/0
Extra: 01c24a91e80fb4bcf0a3386b1d172c61a11d47f891f1b476230c465c800a5d266b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60d2915f6e87a6722ab026d41b10252a215f26a74b32089916d21c71b7794afb 0.600000000000 1446588 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": 986369, "vin": [ { "gen": { "height": 986359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60d2915f6e87a6722ab026d41b10252a215f26a74b32089916d21c71b7794afb" } } ], "extra": [ 1, 194, 74, 145, 232, 15, 180, 188, 240, 163, 56, 107, 29, 23, 44, 97, 161, 29, 71, 248, 145, 241, 180, 118, 35, 12, 70, 92, 128, 10, 93, 38, 107, 2, 17, 0, 0, 0, 2, 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