Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85548456138ab5bf22a78d3b28a3f914e5b0713803768c0f2c38ef4d4e2df18

Tx prefix hash: 31b92fe1dd89f65d0e1c1d9eca6d0a7790d33a051f31e7ddbf963ba7a07b3cdf
Tx public key: 102af68b57ac9d874709fa58623726b52a52012f37b5cec70c10b2089c48cf2d
Timestamp: 1735886390 Timestamp [UCT]: 2025-01-03 06:39:50 Age [y:d:h:m:s]: 00:351:23:08:24
Block: 1189151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249085 RingCT/type: yes/0
Extra: 01102af68b57ac9d874709fa58623726b52a52012f37b5cec70c10b2089c48cf2d0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eb72e750ddd32d424ae7f9f7e9cf81a6d87fdc106ef0464356c266046ef6395 0.600000000000 1675656 of 15

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": 1189161, "vin": [ { "gen": { "height": 1189151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eb72e750ddd32d424ae7f9f7e9cf81a6d87fdc106ef0464356c266046ef6395" } } ], "extra": [ 1, 16, 42, 246, 139, 87, 172, 157, 135, 71, 9, 250, 88, 98, 55, 38, 181, 42, 82, 1, 47, 55, 181, 206, 199, 12, 16, 178, 8, 156, 72, 207, 45, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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