Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d126812c617f5c0144be0d56fd4f93ac793698c7522cbd985dfd7f522ab8d18b

Tx prefix hash: 6d45679a168460deaf89c10ec12cb9d4eb5815e75b9680c2e03bb61fa0eedb4f
Tx public key: 23f1a93ee07919d741201411dff6ead76ddbbefce03651c266ac93e186490a23
Timestamp: 1696786905 Timestamp [UCT]: 2023-10-08 17:41:45 Age [y:d:h:m:s]: 01:100:13:16:54
Block: 865319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333111 RingCT/type: yes/0
Extra: 0123f1a93ee07919d741201411dff6ead76ddbbefce03651c266ac93e186490a23021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.833372137000 dcy

stealth address amount amount idx
00: e1ee50f867ab130fb4d0ab1eee57fb607f9323b7ff61f883e37f4aeaaf91abdc 0.833372137000 1319849 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": 865329, "vin": [ { "gen": { "height": 865319 } } ], "vout": [ { "amount": 833372137, "target": { "key": "e1ee50f867ab130fb4d0ab1eee57fb607f9323b7ff61f883e37f4aeaaf91abdc" } } ], "extra": [ 1, 35, 241, 169, 62, 224, 121, 25, 215, 65, 32, 20, 17, 223, 246, 234, 215, 109, 219, 190, 252, 224, 54, 81, 194, 102, 172, 147, 225, 134, 73, 10, 35, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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