Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434c524db97f12cf287329be61e75f5a009c4d67a9e39a9c588bba6a430b391f

Tx prefix hash: 8334cfc2cef0754571de3f0d03a5df1a756f56854e62693ae114a1b4d73eccca
Tx public key: 97927db68fad0aea70e6424de400b70f9b24f684ef3346ade6cc3053a0aca5e8
Timestamp: 1580791294 Timestamp [UCT]: 2020-02-04 04:41:34 Age [y:d:h:m:s]: 04:364:09:01:07
Block: 58299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151509 RingCT/type: yes/0
Extra: 0197927db68fad0aea70e6424de400b70f9b24f684ef3346ade6cc3053a0aca5e802110000000117786bcf000000000000000000

1 output(s) for total of 393.397895904000 dcy

stealth address amount amount idx
00: fee2c7b66ab36a8743dc24aca08ae994037d2e8bc386fbcf24c8ed7b183c42f7 393.397895904000 107735 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": 58309, "vin": [ { "gen": { "height": 58299 } } ], "vout": [ { "amount": 393397895904, "target": { "key": "fee2c7b66ab36a8743dc24aca08ae994037d2e8bc386fbcf24c8ed7b183c42f7" } } ], "extra": [ 1, 151, 146, 125, 182, 143, 173, 10, 234, 112, 230, 66, 77, 228, 0, 183, 15, 155, 36, 246, 132, 239, 51, 70, 173, 230, 204, 48, 83, 160, 172, 165, 232, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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