Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea0ed3d38abf9157c3f113ce0bb93b1e414000d8d47a0218861e4bf352143dc

Tx prefix hash: 67fe87085eeff039b926534f1b047c9627ed2545c0becee1f63c9e0024ab04bc
Tx public key: bf9a7ff31039cc76def2cf7af0cb2be399723cddc74e6b258ea0f994b642996f
Timestamp: 1578066723 Timestamp [UCT]: 2020-01-03 15:52:03 Age [y:d:h:m:s]: 05:071:20:46:06
Block: 37817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201315 RingCT/type: yes/0
Extra: 01bf9a7ff31039cc76def2cf7af0cb2be399723cddc74e6b258ea0f994b642996f02110000000d4943cd9f000000000000000000

1 output(s) for total of 459.943968966000 dcy

stealth address amount amount idx
00: dbfa6eb7d55f326f9ab4ca0c9818f20c7ee3fa5362921aaa533cfedc024f77bc 459.943968966000 64306 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": 37827, "vin": [ { "gen": { "height": 37817 } } ], "vout": [ { "amount": 459943968966, "target": { "key": "dbfa6eb7d55f326f9ab4ca0c9818f20c7ee3fa5362921aaa533cfedc024f77bc" } } ], "extra": [ 1, 191, 154, 127, 243, 16, 57, 204, 118, 222, 242, 207, 122, 240, 203, 43, 227, 153, 114, 60, 221, 199, 78, 107, 37, 142, 160, 249, 148, 182, 66, 153, 111, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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