Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00f679952364b77590f802560741fa7c74a9a08cbf1c434a016e3a262e4243b

Tx prefix hash: 86e2fd9a8ff407362913621006f01cf15cf5fca97ca992ab6943e5027890631e
Tx public key: 4517f00fa453c188297ebd991d9f7ba9c0d8b62049c410d5cd7ea65588157d58
Timestamp: 1635290960 Timestamp [UCT]: 2021-10-26 23:29:20 Age [y:d:h:m:s]: 04:009:09:47:28
Block: 361166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043527 RingCT/type: yes/0
Extra: 014517f00fa453c188297ebd991d9f7ba9c0d8b62049c410d5cd7ea65588157d5802110000001042b3953e000000000000000000

1 output(s) for total of 39.021820074000 dcy

stealth address amount amount idx
00: 4451c97e3be7f90b013bd61a0bedb44a6ea1c124181bbcf829e7a465405c2f84 39.021820074000 734891 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": 361176, "vin": [ { "gen": { "height": 361166 } } ], "vout": [ { "amount": 39021820074, "target": { "key": "4451c97e3be7f90b013bd61a0bedb44a6ea1c124181bbcf829e7a465405c2f84" } } ], "extra": [ 1, 69, 23, 240, 15, 164, 83, 193, 136, 41, 126, 189, 153, 29, 159, 123, 169, 192, 216, 182, 32, 73, 196, 16, 213, 205, 126, 166, 85, 136, 21, 125, 88, 2, 17, 0, 0, 0, 16, 66, 179, 149, 62, 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