Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ffbf425977a19d1617532a776d106ac9e72978837236c9cfb1d9dffe0d4913

Tx prefix hash: beeb7f3297bc357623163daf4476f7cc11e23f1d8f81e17e84171261c111faf0
Tx public key: 7f87c7d066ccc08968f1a543490661e31551bf199ff9d2d94adfe600855b7a1b
Timestamp: 1578650575 Timestamp [UCT]: 2020-01-10 10:02:55 Age [y:d:h:m:s]: 05:297:06:33:53
Block: 42485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360279 RingCT/type: yes/0
Extra: 017f87c7d066ccc08968f1a543490661e31551bf199ff9d2d94adfe600855b7a1b02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 443.844050365000 dcy

stealth address amount amount idx
00: 176101b2c12a7155e53af04b3e8dcb7f25b2ec28c1852ba26ae6834fd176d4e5 443.844050365000 76568 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": 42495, "vin": [ { "gen": { "height": 42485 } } ], "vout": [ { "amount": 443844050365, "target": { "key": "176101b2c12a7155e53af04b3e8dcb7f25b2ec28c1852ba26ae6834fd176d4e5" } } ], "extra": [ 1, 127, 135, 199, 208, 102, 204, 192, 137, 104, 241, 165, 67, 73, 6, 97, 227, 21, 81, 191, 25, 159, 249, 210, 217, 74, 223, 230, 0, 133, 91, 122, 27, 2, 17, 0, 0, 0, 10, 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