Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6454ed2a427b504ad0498d72e9ca4613fd0d76118be7a957f5cc7cad4233696c

Tx prefix hash: 77a0db1c85ec25410a882305bd96d423c162eb58dbc8158a86178d946b88950d
Tx public key: 8e3835ef7ebcd6cce368e77bd1c2afdd786fd43ade08437c47cf5c3bb309e6e0
Timestamp: 1581088910 Timestamp [UCT]: 2020-02-07 15:21:50 Age [y:d:h:m:s]: 05:001:22:01:43
Block: 60518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153590 RingCT/type: yes/0
Extra: 018e3835ef7ebcd6cce368e77bd1c2afdd786fd43ade08437c47cf5c3bb309e6e002110000003cc71d3ff9000000000000000000

1 output(s) for total of 386.793851021000 dcy

stealth address amount amount idx
00: 18cff7abd35ae04d1a0caebc51c02ae02c09e0869dcee3b63775b42c91c1952e 386.793851021000 111504 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": 60528, "vin": [ { "gen": { "height": 60518 } } ], "vout": [ { "amount": 386793851021, "target": { "key": "18cff7abd35ae04d1a0caebc51c02ae02c09e0869dcee3b63775b42c91c1952e" } } ], "extra": [ 1, 142, 56, 53, 239, 126, 188, 214, 204, 227, 104, 231, 123, 209, 194, 175, 221, 120, 111, 212, 58, 222, 8, 67, 124, 71, 207, 92, 59, 179, 9, 230, 224, 2, 17, 0, 0, 0, 60, 199, 29, 63, 249, 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