Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c88f07dd8511fa290183ef43e4300748b614f9b2cccae7c7517bc26695a8b4

Tx prefix hash: f31d1d041057e0502e5053e868cebf216a3d4add08e40bb5f07f2f43374706f8
Tx public key: 3ba0e0597df02cc425e7447f32cd631db67dcd651f15be2b905a12242c215d63
Timestamp: 1737172601 Timestamp [UCT]: 2025-01-18 03:56:41 Age [y:d:h:m:s]: 00:058:07:17:55
Block: 1199766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41470 RingCT/type: yes/0
Extra: 013ba0e0597df02cc425e7447f32cd631db67dcd651f15be2b905a12242c215d63021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c1e26b27f93fdc4a16222ecda8050889a67cef68c8f2d06f4c03da13d5aa328 0.600000000000 1686399 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": 1199776, "vin": [ { "gen": { "height": 1199766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c1e26b27f93fdc4a16222ecda8050889a67cef68c8f2d06f4c03da13d5aa328" } } ], "extra": [ 1, 59, 160, 224, 89, 125, 240, 44, 196, 37, 231, 68, 127, 50, 205, 99, 29, 182, 125, 205, 101, 31, 21, 190, 43, 144, 90, 18, 36, 44, 33, 93, 99, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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