Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a89568e7ad6934aba8c4c6f2076802b91850bc6b0a550724faa1e5365800ce4

Tx prefix hash: 7619950fda2f729c2a5b6be2b1b74ea30151cfbc8d2c667185de2244447e412c
Tx public key: e8fc2574453c308ce83a8cb0f830593f083f58e91ba9e7ba3805868d703be376
Timestamp: 1630631641 Timestamp [UCT]: 2021-09-03 01:14:01 Age [y:d:h:m:s]: 03:189:16:22:24
Block: 326289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910119 RingCT/type: yes/0
Extra: 01e8fc2574453c308ce83a8cb0f830593f083f58e91ba9e7ba3805868d703be376021100000005a272b9cb000000000000000000

1 output(s) for total of 50.917790046000 dcy

stealth address amount amount idx
00: 6956d5a22b2db15315123b64b5037f0af828dfbf426e0d6fe858889bf48795c3 50.917790046000 676086 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": 326299, "vin": [ { "gen": { "height": 326289 } } ], "vout": [ { "amount": 50917790046, "target": { "key": "6956d5a22b2db15315123b64b5037f0af828dfbf426e0d6fe858889bf48795c3" } } ], "extra": [ 1, 232, 252, 37, 116, 69, 60, 48, 140, 232, 58, 140, 176, 248, 48, 89, 63, 8, 63, 88, 233, 27, 169, 231, 186, 56, 5, 134, 141, 112, 59, 227, 118, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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