Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4c186f71eb1851b6bcffbabadb6e112a9c01de30a01477c45ae2ae291612c8

Tx prefix hash: 434592cfc62fa671edf84132bae7f1aed4bc2c58874480c7b2203e9dad26fc02
Tx public key: 3c68c9546d2b88bf42699f85590b1ed868256c53b4db42d88756124b92f34f9a
Timestamp: 1577804022 Timestamp [UCT]: 2019-12-31 14:53:42 Age [y:d:h:m:s]: 05:107:14:43:04
Block: 35848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226651 RingCT/type: yes/0
Extra: 013c68c9546d2b88bf42699f85590b1ed868256c53b4db42d88756124b92f34f9a02110000001f8a2ee0d9000000000000000000

1 output(s) for total of 466.897499994000 dcy

stealth address amount amount idx
00: 194a8cf9d51dad1ea6e50ef654757f438614dfe701862f94c0d46a2c3ccaa7ac 466.897499994000 60513 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": 35858, "vin": [ { "gen": { "height": 35848 } } ], "vout": [ { "amount": 466897499994, "target": { "key": "194a8cf9d51dad1ea6e50ef654757f438614dfe701862f94c0d46a2c3ccaa7ac" } } ], "extra": [ 1, 60, 104, 201, 84, 109, 43, 136, 191, 66, 105, 159, 133, 89, 11, 30, 216, 104, 37, 108, 83, 180, 219, 66, 216, 135, 86, 18, 75, 146, 243, 79, 154, 2, 17, 0, 0, 0, 31, 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