Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e355665e4de0eabd482fe75147dce3207f9abbcda30785c99798201dc704fae

Tx prefix hash: bf6a55df7f66c3dd418a6c292b4762dffb7c3fa96c40a173ceab0d5fa59cb7ed
Tx public key: 1bafcfc530acdca0d99b78fb8998d2ae915207aae5ef6accb0abf76557a3160d
Timestamp: 1694432909 Timestamp [UCT]: 2023-09-11 11:48:29 Age [y:d:h:m:s]: 01:189:03:57:40
Block: 845780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396300 RingCT/type: yes/0
Extra: 011bafcfc530acdca0d99b78fb8998d2ae915207aae5ef6accb0abf76557a3160d0211000000194b8f5122000000000000000000

1 output(s) for total of 0.967341507000 dcy

stealth address amount amount idx
00: 26ce65d1d25924658ce1fabbb3379e8f91480b129c6c6d37f4a0399dd2a0eca4 0.967341507000 1299198 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": 845790, "vin": [ { "gen": { "height": 845780 } } ], "vout": [ { "amount": 967341507, "target": { "key": "26ce65d1d25924658ce1fabbb3379e8f91480b129c6c6d37f4a0399dd2a0eca4" } } ], "extra": [ 1, 27, 175, 207, 197, 48, 172, 220, 160, 217, 155, 120, 251, 137, 152, 210, 174, 145, 82, 7, 170, 229, 239, 106, 204, 176, 171, 247, 101, 87, 163, 22, 13, 2, 17, 0, 0, 0, 25, 75, 143, 81, 34, 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