Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e513d3061d2a5418cadd85e26ad29d4485750a79c1a66e5afaa796d67fe427de

Tx prefix hash: 4d3f08aa04c259598a8c1763a30b12ea6721e525a16307963de14cf4b0c51698
Tx public key: 42db0087f8e10715be1acde95aff8a92ef3042b02a30002a03dd7dfdf32e24d0
Timestamp: 1704569005 Timestamp [UCT]: 2024-01-06 19:23:25 Age [y:d:h:m:s]: 01:094:17:19:46
Block: 929608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328814 RingCT/type: yes/0
Extra: 0142db0087f8e10715be1acde95aff8a92ef3042b02a30002a03dd7dfdf32e24d002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cda7a53fa82071c8451024dfb07e637caeb86350e32d5d5c8276d2eae2d5157 0.600000000000 1387484 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": 929618, "vin": [ { "gen": { "height": 929608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cda7a53fa82071c8451024dfb07e637caeb86350e32d5d5c8276d2eae2d5157" } } ], "extra": [ 1, 66, 219, 0, 135, 248, 225, 7, 21, 190, 26, 205, 233, 90, 255, 138, 146, 239, 48, 66, 176, 42, 48, 0, 42, 3, 221, 125, 253, 243, 46, 36, 208, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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