Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd65bc47c2c56dfc37e2f92a27f6ce6eea2af0510ba5b29f91912bf20698107e

Tx prefix hash: 93f1bdf0ce2a54736a2a6dbb6c90dcbc533bb9db00acd48a47c743fb317daf63
Tx public key: 7355d9bedcfd6ca3263470313ec941aa1cc74227d7a1fade12992e59a802dfe3
Timestamp: 1576434783 Timestamp [UCT]: 2019-12-15 18:33:03 Age [y:d:h:m:s]: 05:015:09:29:29
Block: 27851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157620 RingCT/type: yes/0
Extra: 017355d9bedcfd6ca3263470313ec941aa1cc74227d7a1fade12992e59a802dfe30211000000048a2ee0d9000000000000000000

1 output(s) for total of 496.371089532000 dcy

stealth address amount amount idx
00: 0cd4655ac0a88fbd704fdf8e3d7e6d2c1f7f90d8784e2647342d91cfc0c255e4 496.371089532000 45969 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": 27861, "vin": [ { "gen": { "height": 27851 } } ], "vout": [ { "amount": 496371089532, "target": { "key": "0cd4655ac0a88fbd704fdf8e3d7e6d2c1f7f90d8784e2647342d91cfc0c255e4" } } ], "extra": [ 1, 115, 85, 217, 190, 220, 253, 108, 163, 38, 52, 112, 49, 62, 201, 65, 170, 28, 199, 66, 39, 215, 161, 250, 222, 18, 153, 46, 89, 168, 2, 223, 227, 2, 17, 0, 0, 0, 4, 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