Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43b166912975f916c479c4dd8dae85d6522803f5e91035d76201650701e4bf13

Tx prefix hash: e014a71a0f41ad07fb09d2491c31663a622d303498e6d8f3823903f37c093882
Tx public key: c8c5e95402695b918d5923a7d5336e1a187bd52a50918e86e13e84925b99727e
Timestamp: 1702498211 Timestamp [UCT]: 2023-12-13 20:10:11 Age [y:d:h:m:s]: 01:341:17:58:22
Block: 912456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503115 RingCT/type: yes/0
Extra: 01c8c5e95402695b918d5923a7d5336e1a187bd52a50918e86e13e84925b99727e02110000001033af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8ee56e47ab7944762d10ee03e77a621a2e7351c9dc98df52d25cb37d4744861 0.600000000000 1369684 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": 912466, "vin": [ { "gen": { "height": 912456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8ee56e47ab7944762d10ee03e77a621a2e7351c9dc98df52d25cb37d4744861" } } ], "extra": [ 1, 200, 197, 233, 84, 2, 105, 91, 145, 141, 89, 35, 167, 213, 51, 110, 26, 24, 123, 213, 42, 80, 145, 142, 134, 225, 62, 132, 146, 91, 153, 114, 126, 2, 17, 0, 0, 0, 16, 51, 175, 153, 244, 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