Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f7adebeaa76e9d17cac2654bb96ae9f9561077aa77101922070c69f6de46222

Tx prefix hash: f40023fd337c963491798af23ceb2a030d11a1c0eb343953686cc56e651a790f
Tx public key: aab545c28b508a376e9e4f5e2686d586a5d98e296cd287bf70839f9375311522
Timestamp: 1578247548 Timestamp [UCT]: 2020-01-05 18:05:48 Age [y:d:h:m:s]: 05:128:15:12:20
Block: 39379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241829 RingCT/type: yes/0
Extra: 01aab545c28b508a376e9e4f5e2686d586a5d98e296cd287bf70839f93753115220211000000e3391a8d0e000000000000000000

1 output(s) for total of 454.497288254000 dcy

stealth address amount amount idx
00: 66fef64d1e8df45791b901b665d6978a48ec1b38bad70685d16d86197c96dc2b 454.497288254000 67861 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": 39389, "vin": [ { "gen": { "height": 39379 } } ], "vout": [ { "amount": 454497288254, "target": { "key": "66fef64d1e8df45791b901b665d6978a48ec1b38bad70685d16d86197c96dc2b" } } ], "extra": [ 1, 170, 181, 69, 194, 139, 80, 138, 55, 110, 158, 79, 94, 38, 134, 213, 134, 165, 217, 142, 41, 108, 210, 135, 191, 112, 131, 159, 147, 117, 49, 21, 34, 2, 17, 0, 0, 0, 227, 57, 26, 141, 14, 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