Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04996330967fa7d7e99d80e4f7810111475091d3ea0a68d6dd43b88d76ebd83e

Tx prefix hash: 83ae6a4dd16590036c8b7b742d89168bbb2a77099345d424a32150d824d9e5ad
Tx public key: b1fda2b673ba040e67c83d3b6f869dbd5520c20ba77c8a5f9c2dae8ae49469d8
Timestamp: 1579120194 Timestamp [UCT]: 2020-01-15 20:29:54 Age [y:d:h:m:s]: 05:294:08:59:04
Block: 46261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358315 RingCT/type: yes/0
Extra: 01b1fda2b673ba040e67c83d3b6f869dbd5520c20ba77c8a5f9c2dae8ae49469d80211000000158a2ee0d9000000000000000000

1 output(s) for total of 431.239904911000 dcy

stealth address amount amount idx
00: 4d8b3d8d14edd23dd541c450710ac9f661537e3167d48967c2e2211b9e452343 431.239904911000 85009 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": 46271, "vin": [ { "gen": { "height": 46261 } } ], "vout": [ { "amount": 431239904911, "target": { "key": "4d8b3d8d14edd23dd541c450710ac9f661537e3167d48967c2e2211b9e452343" } } ], "extra": [ 1, 177, 253, 162, 182, 115, 186, 4, 14, 103, 200, 61, 59, 111, 134, 157, 189, 85, 32, 194, 11, 167, 124, 138, 95, 156, 45, 174, 138, 228, 148, 105, 216, 2, 17, 0, 0, 0, 21, 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