Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59674a87e50f47e5d3abf4857a173e37f1d07693c462191121fe07d3dd640dff

Tx prefix hash: 31ae9893519993aef3782765d19a556b047c6b9e40b517aca4996d739d8f711b
Tx public key: 55dc35b60e35a885009b4aaf046a469c8c9a9a45d60e5775d542ba712d6fb3d4
Timestamp: 1662048560 Timestamp [UCT]: 2022-09-01 16:09:20 Age [y:d:h:m:s]: 02:069:14:46:03
Block: 578608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571181 RingCT/type: yes/0
Extra: 0155dc35b60e35a885009b4aaf046a469c8c9a9a45d60e5775d542ba712d6fb3d402110000001875e3f0e9000000000000000000

1 output(s) for total of 7.427310751000 dcy

stealth address amount amount idx
00: c1afaca4b6249349eb873f6d9c583a4e81c514608c89d5f92f880f52a47669d0 7.427310751000 1012026 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": 578618, "vin": [ { "gen": { "height": 578608 } } ], "vout": [ { "amount": 7427310751, "target": { "key": "c1afaca4b6249349eb873f6d9c583a4e81c514608c89d5f92f880f52a47669d0" } } ], "extra": [ 1, 85, 220, 53, 182, 14, 53, 168, 133, 0, 155, 74, 175, 4, 106, 70, 156, 140, 154, 154, 69, 214, 14, 87, 117, 213, 66, 186, 113, 45, 111, 179, 212, 2, 17, 0, 0, 0, 24, 117, 227, 240, 233, 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