Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed8319e62ea1327bb6c958a943bfbad23193e821d530b7f52f8000bf4655bf1

Tx prefix hash: bc396cf8cd183ec9b1fdbac4f9a60e5868c67f12f6f50ff60b2dee2a38bd7b50
Tx public key: cfbbfad6f2da98a69e83370267bfe5bc781ccd6af99467e9e93c3bdc4a28674b
Timestamp: 1577399060 Timestamp [UCT]: 2019-12-26 22:24:20 Age [y:d:h:m:s]: 05:158:13:24:28
Block: 32482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1263123 RingCT/type: yes/0
Extra: 01cfbbfad6f2da98a69e83370267bfe5bc781ccd6af99467e9e93c3bdc4a28674b0211000000138a2ee0d9000000000000000000

1 output(s) for total of 479.043011355000 dcy

stealth address amount amount idx
00: f7b90a7c5824cd105fcd70b91b87c243f2b4958319ce856bfcdd08a185f4e6e3 479.043011355000 54029 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": 32492, "vin": [ { "gen": { "height": 32482 } } ], "vout": [ { "amount": 479043011355, "target": { "key": "f7b90a7c5824cd105fcd70b91b87c243f2b4958319ce856bfcdd08a185f4e6e3" } } ], "extra": [ 1, 207, 187, 250, 214, 242, 218, 152, 166, 158, 131, 55, 2, 103, 191, 229, 188, 120, 28, 205, 106, 249, 148, 103, 233, 233, 60, 59, 220, 74, 40, 103, 75, 2, 17, 0, 0, 0, 19, 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