Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a1d390ea30041d931e13f91cc0c9fe17309b3a37a13a77fb11f20faeb589d0

Tx prefix hash: 29627ee81e9449889ebfc78815f38d99850f806bc4302d6a12e1990e2ff4343c
Tx public key: 9e0aa3bf65cb7548d55ff430503d52eafffe41edf510f374cac1156709ad9e88
Timestamp: 1578008982 Timestamp [UCT]: 2020-01-02 23:49:42 Age [y:d:h:m:s]: 05:035:20:23:33
Block: 37477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175384 RingCT/type: yes/0
Extra: 019e0aa3bf65cb7548d55ff430503d52eafffe41edf510f374cac1156709ad9e880211000000088a2ee0d9000000000000000000

1 output(s) for total of 461.130653642000 dcy

stealth address amount amount idx
00: 202040aef4901ed7c3cb09db42fdf60dc4709e04bd1b5b7b2dbf538bdfd6218d 461.130653642000 63641 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": 37487, "vin": [ { "gen": { "height": 37477 } } ], "vout": [ { "amount": 461130653642, "target": { "key": "202040aef4901ed7c3cb09db42fdf60dc4709e04bd1b5b7b2dbf538bdfd6218d" } } ], "extra": [ 1, 158, 10, 163, 191, 101, 203, 117, 72, 213, 95, 244, 48, 80, 61, 82, 234, 255, 254, 65, 237, 245, 16, 243, 116, 202, 193, 21, 103, 9, 173, 158, 136, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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