Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bd0436e1e0ac028b8e2b054c16d1d3f9a5460364a66d0021479f950863603b2

Tx prefix hash: be73d16760061824d2a7fd11bdd561a2821b69dfd5c9e796fbf409f3bed82320
Tx public key: 769a250eefcc9b8a688bf3e88965a0f0725bb22f0f25a5d703f75aae6b812aa7
Timestamp: 1577713652 Timestamp [UCT]: 2019-12-30 13:47:32 Age [y:d:h:m:s]: 05:003:16:58:16
Block: 35067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152625 RingCT/type: yes/0
Extra: 01769a250eefcc9b8a688bf3e88965a0f0725bb22f0f25a5d703f75aae6b812aa7021100000004d81c26c0000000000000000000

1 output(s) for total of 469.687851043000 dcy

stealth address amount amount idx
00: b239c9a9258db052b66f9a24b36f754c04becb4eeadd518ae229c453c8001e80 469.687851043000 59070 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": 35077, "vin": [ { "gen": { "height": 35067 } } ], "vout": [ { "amount": 469687851043, "target": { "key": "b239c9a9258db052b66f9a24b36f754c04becb4eeadd518ae229c453c8001e80" } } ], "extra": [ 1, 118, 154, 37, 14, 239, 204, 155, 138, 104, 139, 243, 232, 137, 101, 160, 240, 114, 91, 178, 47, 15, 37, 165, 215, 3, 247, 90, 174, 107, 129, 42, 167, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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