Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bad272ba8d9dea517d9df409059919e72e6682990bc7d2228763db627e0e03cd

Tx prefix hash: 3e14f1f957be87479bd8720228fd7c6496d82cc4ad10454cebf0a8e3b3eb8033
Tx public key: 0dc22ef4b38c3e8f0a0e530f4b2afdd0751b7d3fc8cd2f658b590801f55e52e3
Timestamp: 1580900672 Timestamp [UCT]: 2020-02-05 11:04:32 Age [y:d:h:m:s]: 05:074:07:42:07
Block: 59269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205061 RingCT/type: yes/0
Extra: 010dc22ef4b38c3e8f0a0e530f4b2afdd0751b7d3fc8cd2f658b590801f55e52e30211000000babd0f9f9f000000000000000000

1 output(s) for total of 390.497284958000 dcy

stealth address amount amount idx
00: 005ef206269cb82abbd8aaa2b86f57439c6f8c93b61d130e24aeba613be85a1a 390.497284958000 109417 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": 59279, "vin": [ { "gen": { "height": 59269 } } ], "vout": [ { "amount": 390497284958, "target": { "key": "005ef206269cb82abbd8aaa2b86f57439c6f8c93b61d130e24aeba613be85a1a" } } ], "extra": [ 1, 13, 194, 46, 244, 179, 140, 62, 143, 10, 14, 83, 15, 75, 42, 253, 208, 117, 27, 125, 63, 200, 205, 47, 101, 139, 89, 8, 1, 245, 94, 82, 227, 2, 17, 0, 0, 0, 186, 189, 15, 159, 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