Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 514f4f0368dafd24e8a61d5a90a63e56a7ba7d2080251061d97f7c41cfeab5b2

Tx prefix hash: 3831196aeef493fe8473e1196a77912dc0f46f26351ab5818b44d22747debc1e
Tx public key: c0f8a1a2f1662d6b80a0cdc137aaa7d008c8e40b4a2f0d3ee25d45382a702868
Timestamp: 1581090705 Timestamp [UCT]: 2020-02-07 15:51:45 Age [y:d:h:m:s]: 04:293:07:01:58
Block: 60671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101039 RingCT/type: yes/0
Extra: 01c0f8a1a2f1662d6b80a0cdc137aaa7d008c8e40b4a2f0d3ee25d45382a702868021100000001026b59f3000000000000000000

1 output(s) for total of 386.342609275000 dcy

stealth address amount amount idx
00: eb7ac57dec6d3c8191206e5328f9e4d7b828ff9ccffae2bd8b4cac2e1233266e 386.342609275000 111711 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": 60681, "vin": [ { "gen": { "height": 60671 } } ], "vout": [ { "amount": 386342609275, "target": { "key": "eb7ac57dec6d3c8191206e5328f9e4d7b828ff9ccffae2bd8b4cac2e1233266e" } } ], "extra": [ 1, 192, 248, 161, 162, 241, 102, 45, 107, 128, 160, 205, 193, 55, 170, 167, 208, 8, 200, 228, 11, 74, 47, 13, 62, 226, 93, 69, 56, 42, 112, 40, 104, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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