Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 336b94dd547579d6671aa90fe136ea584ed1e57f84d97b88344fa1306a522324

Tx prefix hash: 377dde90a8bf909f3b6e7af9b9fe3f9fb4318cc91211607594ecd10c0729bfbc
Tx public key: 96a9209f558a042964a1fb6a8a9e639a8a51e83b06f1ef4bdaddcaf3d72a8d11
Timestamp: 1661440383 Timestamp [UCT]: 2022-08-25 15:13:03 Age [y:d:h:m:s]: 01:364:09:10:56
Block: 573584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520945 RingCT/type: yes/0
Extra: 0196a9209f558a042964a1fb6a8a9e639a8a51e83b06f1ef4bdaddcaf3d72a8d1102110000000475e3f0e9000000000000000000

1 output(s) for total of 7.717527749000 dcy

stealth address amount amount idx
00: da5f3cbfe741019cb006ddafa043a0ac4fb77a9922d38615c0e6ce2e506d4540 7.717527749000 1006878 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": 573594, "vin": [ { "gen": { "height": 573584 } } ], "vout": [ { "amount": 7717527749, "target": { "key": "da5f3cbfe741019cb006ddafa043a0ac4fb77a9922d38615c0e6ce2e506d4540" } } ], "extra": [ 1, 150, 169, 32, 159, 85, 138, 4, 41, 100, 161, 251, 106, 138, 158, 99, 154, 138, 81, 232, 59, 6, 241, 239, 75, 218, 221, 202, 243, 215, 42, 141, 17, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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