Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0a63bebc05769f608fcfc993eab1ad2aba7e74ad256d2ada7f6108f7f5c0b8

Tx prefix hash: ecce0c8fd194ed20db3282e6f0a876b348f6e119e95e9ca3e72bc986104bafdd
Tx public key: 47db6ace61bbd74e479ab446e55eef7e7ecf51281e6c78a5bc192e62597910f3
Timestamp: 1706406060 Timestamp [UCT]: 2024-01-28 01:41:00 Age [y:d:h:m:s]: 01:137:03:26:46
Block: 944833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359079 RingCT/type: yes/0
Extra: 0147db6ace61bbd74e479ab446e55eef7e7ecf51281e6c78a5bc192e62597910f302110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf1ae7cbcf6d614681c52616f3e97f7feeafbb16d95ef153542fe97cbdeb0dfb 0.600000000000 1403119 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": 944843, "vin": [ { "gen": { "height": 944833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf1ae7cbcf6d614681c52616f3e97f7feeafbb16d95ef153542fe97cbdeb0dfb" } } ], "extra": [ 1, 71, 219, 106, 206, 97, 187, 215, 78, 71, 154, 180, 70, 229, 94, 239, 126, 126, 207, 81, 40, 30, 108, 120, 165, 188, 25, 46, 98, 89, 121, 16, 243, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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