Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f2824824e142e36a0a40bf75ae1a1d2ebb1a99708f85a430fe276b7fc8288c

Tx prefix hash: e9f87c1c5fdc45d69a540e7f36701a8596ecaf44265c35903576c56f0e9c2943
Tx public key: 3e11ccb1b7cdf28d4a528b39d4834aca72a5878fd55590964915f4b3d3e518e8
Timestamp: 1616413759 Timestamp [UCT]: 2021-03-22 11:49:19 Age [y:d:h:m:s]: 03:318:07:11:41
Block: 224016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986667 RingCT/type: yes/0
Extra: 013e11ccb1b7cdf28d4a528b39d4834aca72a5878fd55590964915f4b3d3e518e80211000000079c1fbdcc000000000000000000

1 output(s) for total of 111.107298684000 dcy

stealth address amount amount idx
00: 2e44ecc1025ddbb3b0d0240e9c862112d87a0fdc9dff53a01042bc4f21b0e50e 111.107298684000 462722 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": 224026, "vin": [ { "gen": { "height": 224016 } } ], "vout": [ { "amount": 111107298684, "target": { "key": "2e44ecc1025ddbb3b0d0240e9c862112d87a0fdc9dff53a01042bc4f21b0e50e" } } ], "extra": [ 1, 62, 17, 204, 177, 183, 205, 242, 141, 74, 82, 139, 57, 212, 131, 74, 202, 114, 165, 135, 143, 213, 85, 144, 150, 73, 21, 244, 179, 211, 229, 24, 232, 2, 17, 0, 0, 0, 7, 156, 31, 189, 204, 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