Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff24dc57e12b0f14b5bc84d0dffa4f54b2071eb2ae0f0196fce3e935aaa2983

Tx prefix hash: 612ac1a076742031882139cfdf6464c73c1496fa07c03616d7e5fd64f61ec72f
Tx public key: e943a4eb3fd7f041a4e9304394b3650b2398b2f754e3dd0bcfae006f6d41b98f
Timestamp: 1580118912 Timestamp [UCT]: 2020-01-27 09:55:12 Age [y:d:h:m:s]: 04:336:15:00:55
Block: 53922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130732 RingCT/type: yes/0
Extra: 01e943a4eb3fd7f041a4e9304394b3650b2398b2f754e3dd0bcfae006f6d41b98f0211000000054ac5aa02000000000000000000

1 output(s) for total of 406.756832889000 dcy

stealth address amount amount idx
00: c385f65fdcbc542d2a8173fe66ff567369a2fb77b51a0f92238fcee9ad97fd63 406.756832889000 99906 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": 53932, "vin": [ { "gen": { "height": 53922 } } ], "vout": [ { "amount": 406756832889, "target": { "key": "c385f65fdcbc542d2a8173fe66ff567369a2fb77b51a0f92238fcee9ad97fd63" } } ], "extra": [ 1, 233, 67, 164, 235, 63, 215, 240, 65, 164, 233, 48, 67, 148, 179, 101, 11, 35, 152, 178, 247, 84, 227, 221, 11, 207, 174, 0, 111, 109, 65, 185, 143, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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